I agree completely with you, Jeff.

However, I think it somehow would be nice, if you guys could tell comming users that the win32 solution is geared toward VC++ 7.1 (and hence use of other tools are at their own risk).

And, I think it also would be really cool, if you guys come up with a solution how to handle multiple VC++ x solutions/projects from the same source, possibly ranging from VC 6.0 to future releases.

Another future solution could be that the VC++ x tools get incorparted into the makefile structure, as previously discussed. It appeared to me that the mingw or gunwin32 environment mixed with the VC++ x tools could be a solution.

Henrik.

----Original Message Follows----

It's a possibility, though it would be better to create whole separate trees for different versions of VS. It's not just the project and solutions that need to be kept separate; the object files themselves cannot be mixed between different versions of VS.

There's no rush though. Trust me, C/C++ programmers will not rush to adopt Whidbey once it's released. You'd be amazed at the amount of commercial Windows software development that still uses VC++ 6.0 even today. And that's with 7.1 offering real advantages to C++ programmers over 7.0, which itself had real advantages over 6.0. I've yet to see anything for us in 8.0. I can't imagine upgrading before 8.1 or even 9.0, and then with reluctance.

Henrik Bach wrote: